Storage system

ABSTRACT

When a computer  10  receives a request from the client computer  30  to access snapshot files, the target device to be used is identified. The computer  10  makes a request to the identified target device TD for attachment of the logical device LDEV that stores the snapshot files for which access is requested. When the computer  10  receives notification that the attachment has ended from the storage device system  20 , the identified target device is mounted on the directory in which the snapshot files are stored.

This application is a continuation application of U.S. Ser. No. 11/373,089, filed Mar. 13, 2006, which is a continuation-in-part of U.S. patent application Ser. No. 11/132,176 filed on May 19, 2005, and which claims priority to Japanese Patent Application No. 200587475 filed on Mar. 25, 2005 and Japanese Patent Application No. 2006-15741 filed on Jan. 25, 2006, the disclosures of all of which are also entirely incorporated herein by reference.

BACKGROUND

The present invention relates to a storage system comprising a storage device system comprising a computer and a plurality of logical storage areas.

Generally, for a storage system, a computer (file system) is able to access desired files (storage areas) in a storage device system via a target device. The target device is a logical device on a storage device system recognizable as subject to access from the computer, and is provided virtually using software, or physically using hardware. The target devices are uniformly correlated to the storage areas, and the computer is able to access the desired storage area by identifying a target device using a port ID (e.g. an identifier for uniformly identifying a port called a WWN (World Wide Name)) and an LUN (Logical Unit Number).

However, when there is a limit to the number of target devices that may be provided by the storage device system, the data capacity that may be stored in the storage device system is limited by the target device count. Also, even when there is a not a de facto limit in the number of target devices that may be provided by the storage device system, the number of target devices increases together with an increase in the file count, and there is the problem that the target device resources for the storage device system are consumed.

These problems become severe when executing a point in time copy for which it is possible to reproduce the storage state of the storage device system at an identified point in time, a so-called snapshot. Specifically, the storage device system is a system for storing data sent successively from the client computer, and when the target device resources decrease due to an increase in the number of snapshot files, the number of target devices to be allocated to the new storage areas for storing data written from the client computer also decreases. Also, when there is a limit to the number of target devices, even when there are sufficient empty areas for storing the data in the storage device system, the storage device system may not store the information originally to be stored, and there is the risk of hindrance to the function to be provided by the storage device system for storing the snapshot files.

SUMMARY

The present invention is created in order to address at east part of the problems noted above, and its purpose is to provide effective use of the target device resources for the storage device system of the storage system.

The first aspect of the present invention for addressing the problems noted above provides a storage system having a computer and a storage device system, wherein the storage device system is accessed by the computer and has a plurality of logical storage areas. In the storage system of the first aspect of the present invention,

the computer comprises a receiving unit that receives requests to access one storage area of computer among a plurality of storage area of computers, wherein the storage area of computers are recognized by the computer and corresponding to the plurality of logical storage areas, target device identification module that identifies a target device to be mounted in the storage area of computer for which access is requested from among the plurality of target devices, wherein the plurality of target devices are recognized by the computer as subjects for access in the storage device system, mounting module that mounts the identified target device on the storage area of computer for which the access is requested, and a transmission unit that transmits to the storage device system an access request to the storage area corresponding to the storage area of computer for which the access is requested,

and the storage device system comprises one or a plurality of physical storage devices forming the plurality of logical storage areas, the plurality of target devices for which one logical storage area of the plurality of logical storage areas is allocated, a receiving unit that receives the access request transmitted from the computer, and an allocation change module that allocates the logical storage area for which the access is requested to the identified target device according to the access request.

According to the storage system of the first aspect of the present invention, the computer identifies the target device to be mounted in the requested storage area of computer from among the plurality of target devices recognized as subject to access for the storage device system, and transmits to the storage device the access request that is the request for access via the identified target device, and the storage device system allocates the storage area corresponding to the storage area of computer for which the access is requested in relation to the identified target device according to the access request transmitted from the computer, so it is possible to try to achieve effective use of the target device resources for the storage device system of the storage system.

The second aspect of the present invention provides a storage system comprising a computer and a storage device system having a physical storage area for storing the primary information and a logical storage area for storing information for providing the primary information at any time. In the storage system of the second aspect of the invention,

the computer comprises a receiving unit that receives access requests to the primary information at the any time, target device identification module that identifies the target device to be mounted in the storage area of computer from among a plurality of target devices recognized by the computer as subject to access, wherein the storage area of computer is corresponding to the storage area for storing the information for providing the primary information at the requested any time, and a transmission unit that transmits to the storage device system the access request to the storage area that stores information for providing the primary information at the requested any time,

and the storage device system comprises one or a plurality of physical storage devices for forming the plurality of logical storage areas, the plurality of target devices for which one logical storage area of the plurality of the logical storage areas is allocated, a receiving unit that receives the access request transmitted from the computer, and allocation change module that allocates the storage area for storing information for providing the primary information at any time when the access is requested to the identified target device according to the access request.

According to the storage system of the second aspect of the present invention, the computer identifies the target device to be mounted in the storage area of computer for storing the information for providing the primary information at the requested any time from among the plurality of target devices recognized as subject to access, and transmits to the storage device the access request that is the request for access to the storage area for storing the information for providing the primary information at the requested any time via the identified target device, and the storage device system allocates the storage area for storing the information for providing the primary information at any time for which access to the identified target devices is requested according to the access request transmitted from the computer, so it is possible to attempt to achieve effective use of the target device resources for the storage device system of the storage system.

The third aspect of the present invention provides a computer for accessing a storage device system comprising one or a plurality of storage devices for forming a plurality of logical storage areas. The computer of this third aspect of the present invention comprises storage area of computer provision module that provides the plurality of storage area of computer identified by the computer respectively to the plurality of storage areas, a receiving unit that receives access requests to one storage area of computer from among the plurality of storage area of computer, target device identification module that identifies the target device to be mounted on the requested storage area of computer from among the plurality of target devices recognized by the computer as subject to access for the storage device system, mount decision module that determines whether the target device to be correlated to the requested storage area of computer is mounted on another storage area of computer, unmounting module that unmounts the target device when the target device to be correlated to the requested storage area of computer is mounted on the other storage area of computer, mounting module that mounts the target device to the requested storage area of computer after receiving allocation completion notification from the storage device system, and a transmission unit that transmits to the storage device the access request via the identified target device to the storage area corresponding to the requested storage area of computer.

According to the computer of the third aspect of the present invention, the target device to be mounted in the requested storage area of computer is identified from among the plurality of target devices, a determination is made of whether or not the target device corresponding to the requested storage area of computer is mounted in another storage area of computer, and when the target device corresponding to the requested storage area of computer is mounted in another storage area of computer, the target device is unmounted, and after receiving the allocation completion notification from the storage device system, the target device is mounted in the requested storage area of computer, and the access request in relation to the storage area of the storage device system corresponding to the requested storage area of computer is transmitted to the storage device via the identified target device, so it is possible to attempt to achieve effective use of the target device resources for the storage device system of the storage system.

In addition to the storage system and the computer, the present invention additionally achieves realization of a storage system control method, a computer control method, a storage system control program, a computer control program, and a computer readable recording medium on which these control programs are recorded. Other aspects and advantages of the present invention will become apparent from the following detailed description, taken in conjunction with the accompanying drawings, illustrating by way of example the principles of the present invention.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention will be readily understood by the following detailed description in conjunction with the accompanying drawings. To facilitate this description, like reference numerals designate like structural elements.

FIG. 1 is an explanatory drawing showing the schematic structure of the storage system of the first embodiment.

FIG. 2 is an explanatory drawing conceptually showing the various programs and modules stored in the memory of the computer included in the storage system of the first embodiment.

FIG. 3 is an explanatory drawing showing an example of the table for storing the snapshot management information.

FIG. 4 is an explanatory drawing showing an example of the table for storing the directory device information.

FIG. 5 is an explanatory drawing showing an example of the table for storing the device mount information.

FIG. 6 is an explanatory drawing showing an example of the table for storing the device mount information.

FIG. 7 is an explanatory drawing conceptually showing the various programs and modules stored in the memory of the storage device system included in the storage system of the first embodiment.

FIG. 8 is an explanatory drawing showing an example of the table for storing the device attachment information.

FIG. 9 is an explanatory drawing showing an example of the table for storing the device attachment information when using the virtual volume.

FIG. 10 is an explanatory drawing showing an example of the table for storing the snapshot management information.

FIG. 11 is an explanatory drawing showing an example of the table for storing the snapshot detailed management information.

FIG. 12 is an explanatory drawing showing an example of the table for storing the snapshot detailed management information.

FIG. 13 is an explanatory drawing typically showing the correlation of the snapshot file information and the target device information recognized by the file system of the computer, and the target device and the logical device for the storage device system.

FIG. 14 is a flow chart showing the processing routine executed for the routine of accessing the mirroring type snapshot files.

FIG. 15 is a flow chart showing the processing routine executed when acquiring the mirroring type snapshot file.

FIG. 16 is an explanatory drawing typically showing the correlation of the snapshot file information and the target device information recognized by the file system of the computer, and the logical device and the snapshot data group stored in the storage pool.

FIG. 17 is a flow chart showing the processing routine executed for the process of accessing the copy on write type snapshot files.

FIG. 18 is a flow chart showing the processing routine executed when acquiring the copy on write type snapshot file.

FIG. 19 is an explanatory drawing typically showing the correlation between the snapshot file information and the target device information recognized by the computer file system, the target device and logical device of the storage device system, and the primary side volume file data groups and snapshot data groups stored in the logic device and the storage pool.

FIG. 20 is an explanatory drawing showing an example of a table that stores the device attachment information for the variation example.

FIG. 21 is an explanatory drawing showing an example of a table that stores the snapshot detailed management information for the variation example.

FIG. 22 is an explanatory drawing showing the schematic structure of the storage system 100A of another embodiment.

FIG. 23 is an explanatory drawing typically showing the correlation between the file information and target device information recognized by the computer file system, and the storage device system target device and logical device for the fourth embodiment.

FIG. 24 is an explanatory drawing showing in detail the file management information table used for the fourth embodiment.

FIG. 25 is a flow chart showing the processing routine executed for the process of accessing the files for the storage device system of the fourth embodiment.

FIG. 26 is an explanatory drawing typically showing the correlation between the file information and target device information recognized by the computer file system and the file data groups of the storage device system of the fifth embodiment.

FIG. 27 is an explanatory drawing showing an example of a table that stores the device attached information of the fifth embodiment.

FIG. 28 is a flow chart showing the processing routing executed for the process of accessing the virtual volume file for the storage device system of the fifth embodiment.

FIG. 29 is an explanatory drawing showing an example of the client identification table comprised by the computer.

FIG. 30 is an explanatory drawing typically showing the correlation between the file information and target device information recognized by the computer file system and the target device and logical device of the storage device system in other embodiments.

FIG. 31 is a flow chart showing the processing routine executed for the inquiry process.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

Following, the storage system of the present invention is described based on several embodiments while referencing the drawings.

First Embodiment System Configuration

The schematic structure of the storage system of the first embodiment is described while referencing FIG. 1. FIG. 1 is an explanatory drawing showing the schematic structure of the storage system of the first embodiment.

The storage system 100 of the first embodiment comprises a computer 10 and a storage device system 20 accessed by the computer 10. A client computer 30 and 31, a management server 50, and a service host 51 are connected via a network 40 or are directly connected to the storage system 100. With the storage system 100 of the first embodiment, the computer 10 and the storage device system 20 are stored in the same case, and this is identified as a file server from external computers. Also, because the computer 10 and the storage device system 20 are stored in the same case, writing and reading of files and generation of files are executed using common control commands between the computer 10 and the storage device system 20.

The computer 10 of the first embodiment is connected to the client computers 30 and 31 via the network 40. The network 40 is a local area network (LAN) built using the Ethernet (registered trademark), and data transmission is executed using the TCP/IP protocol as the communication protocol. The client computers 30 and 31 are external computers that use the storage system 100, and request file write, read, and generation to the storage device system 20 via the computer 10 within the storage system 100.

The computer 10 internally comprises a central processing unit (CPU) 11, memory 12, and a LAN interface 13. The CPU 11, the memory 12, and the LAN interface 13 are mutually connected via a bus. The CPU 11 is the operation processing device for executing various types of programs and modules stored in the memory 12. The memory 12 is a so-called internal storage device, and comprises both non-volatile memory for storing various modules and the like and volatile memory for temporarily storing the operation processing results. The LAN interface 13 is connected to the network 40, and executes sending and receiving of commands and data between the client computers 30 and 31 using the TCP/IP protocol.

The storage device system 20 comprises the central processing unit (CPU) 21, the memory 22, the FC interface 23 and 26, a plurality of disk devices 24, a disk interface 25, and a LAN interface 27. The CPU 21 executes various control processes for the storage device system 20 by executing various programs and modules stored in the memory 22. The memory 22 is a so-called internal storage device, and comprises both non-volatile memory for storing various modules and the like and volatile memory for temporarily storing the operation processing results.

The FC interface 23 is connected using optical fiber cable or copper wire, for example, and executes sending and receiving of commands and data between the computer 10 and the storage device system 20 using the fiber channel protocol.

The disk device 24 is a disk array device made by RAID construction from a plurality of magnetic hard disk drives, and provides one or a plurality of storage areas, specifically, logical devices (LDEV) using the plurality of hard disk drives, or provides one or a plurality of logical devices by one hard disk drive. Access to each of the logical devices (also called logical units) is executed using the logical unit number (LUN) and the logical block address (LBA).

The CPU 21 is connected to the disk device 24 via the disk interface 25. The disk interface 25 converts the logical addresses transmitted from the CPU 21 to the logical block addresses, and access to each of the logical devices is realized by the CPU 21.

A service host computer 51 is connected to the FC interface 26 via the optical fiber cable, or the service host computer 51 is connected via an SAN (Storage Area Network). The service host computer 51 executes work programs such as a database management system (DBMS), writes the processing results to the storage device system 20, or uses the information resources stored in the storage device system 20. With SAN, fiber channel and iSCSI communication protocol are used.

The client computers 30 and 31 are terminal devices for inputting or outputting various types of data to the storage device system 20, for example, and may also comprise one unit or three or more units. Note that the client computers 30 and 31 may also be connected to the service host 51 via the network 40, and may be connected to the storage device system 20 via the application program that is implemented ins the service host 51.

The management server 50 is a management computer for executing management on the storage system 100, for example, creation of volumes on the storage device system 20, allocation to the host, zoning, and setting of LUN masking. The management server 50 is connected to the LAN interface 27 of the storage device system 20 via the LAN interface 28 of the storage system 100, and executes sending and receiving of commands and data between the storage device system 20 using the TCP/IP protocol.

The various programs and modules stored in the memory 12 of the computer 10 will be described while referencing FIG. 2 to FIG. 6. FIG. 2 is an explanatory drawing conceptually showing the various programs and modules stored in the memory 12 of the computer 10 contained in the storage system of the first embodiment of FIG. 2. FIG. 3 is an explanatory drawing showing an example of the table for storing the snapshot management information. FIG. 4 is an explanatory drawing showing an example of the table for storing the directory device information. FIG. 5 is an explanatory drawing showing an example of the table for storing the device mount information. FIG. 6 is an explanatory drawing showing an example of the table for storing the device mount information.

With this embodiment, following, an example is described of storing snapshot files for the storage system 10 in the logical device. Stored in the memory 12 are the operating system OS for realizing the backbone processes of the computer 10, the storage device system management process program FP for operating on the operating system OS, the snapshot management information table CT1, the device mount information table CT2, the directory device information table CT3, and the usable device information table CT4.

The storage device system management program FP is a program for managing access to the storage device system 20, and contains several execution modules. The request receiving module Mc1 receives requests for access to the computer side logical device (directory) identified by the computer 10 from the client computers 30 and 31. When the request receiving module Mc1 receives a request to access an identified computer side logical device, the target device identification module Mc2 identifies the target device to be mounted in the computer side logical devices for which access is requested. Here, the target device is the logical device that may be recognized as the device subject to access when the computer 10 accesses the storage device system 20, and is defined by the port ID and the LUN. Specifically, the computer 10 is able to access the desired logical device corresponding to the computer side logical device via the target device that has the port role for the storage device system 20. Generally, the target device and the computer side logical device have a uniform relationship and the path is fixed, but with this embodiment, one or a plurality of computer side logical devices are dynamically allocated to one target device, so the path for the logical device changes. Note that the target device may also be the plurality of physical ports comprised in the storage device system 20, or may also be the virtual port provided logically by the port provision module comprised by the storage device system 20.

The mount decision module Mc3 determines whether the target device identified by the target device identification module Mc2 is already mounted in another computer side logical device. Specifically, as described previously, with this embodiment, a plurality of computer side logical devices may be allocated to the target device, so this determination is necessary. The mounting module Mc4 mounts the identified target device to the computer side requested logical device for which access is requested. As a result, the computer 10 is capable of accessing the logical device of the storage device system 20 corresponding to the computer side requested logical device via the target device. Note that with this embodiment, to prevent erroneous access to another logical device, after receiving notification to the effect that attachment is completed for the requested logical device to the identified target device from the storage device system 20 side, the mount action module Mc4 mounts the identified target device to the computer side requested logical device.

The unmount action module Mc5 cancels the mounting of the target device to the computer side logical device. As a result, the computer 10 is not able to access the logical device of the storage device system 20 corresponding to the computer side requested logical device via the target device. Note that the actual entity comprising the target device and the logical device is the storage device system 20, and at the computer 10, the process of mounting and unmounting the computer side target device on the computer side logical device (directory) realized by software is executed on the operating system (file system). At the storage device system 20 side, as described previously, attachment (allocation) or detachment (allocation release) of the target device and the logical device is executed corresponding to the mounting and unmounting of the identified target device for the computer side requested logical device for the computer 10. With the description that follows, the target device (target device information) recognized on the operation system of the computer 10 is the target device Dev, and the actual target device for the storage device system 20 is the target device TD. Also, the computer side storage area (storage area of computer) is called the directory, and the storage area of the storage device system 20 is called the logical device LDEV. Furthermore, the logical device LDEV is also called the logical unit LU.

The Input/Output request reserve module Mc6 transmits to the storage device system 20 the command for requesting access to the logical device of the storage device system 20 corresponding to the computer side requested logical device. The commands contain information for identifying the logical device to be attached to the target device.

The point in time copy request module Mc7 is the module for requesting a point in time copy, acquisition of so-called snapshot files, to the storage device system 20. The snapshot is technology for copying an identified volume (directory) at an identified point in time, or of acquiring the difference data in relation to the original volume and reproducing the volume for the identified point in time. Generally, the former is the mirroring type snapshot executed by copying an identified volume at an identified point in time to another volume, and the latter is the copy on write type snapshot executed by saving the information prior to changing for the changed part in relation to the original volume to another volume. In either case, it is possible to call an identified volume at an identified point in time (generation) from the client computers 30 and 31.

The directory provision module Mc8 provides the computer side storage area (directory) corresponding to the storage areas (logical device) comprised by the storage device system 20. Specifically, identification and operation of the logical devices existing on the storage device system 20 side are made possible on the computer 10 side via the directory. This module function is provided using the file system for example.

The snapshot management information table CT1 is described while referencing FIG. 3. The snapshot system comprises a pair consisting of a primary volume (main volume) of which a snapshot is taken and a volume for storing the snapshot (secondary volume). Therefore, the snapshot management information table CT1 contains the snapshot primary side information and the secondary information. The primary information has the primary directory information stored in it, and the secondary information contains the ID that indicates the snapshot generation, the stored directory information, and information indicating whether or not the snapshot is acquired, specifically, information indicating whether or not the snapshot file is stored. The example in FIG. 3 comprises a pair consisting of the primary directory (/mnt/home) and each secondary directory (/mnt/ss/home_sN), and the snapshot files are stored in the secondary directories of ID=1 to 3.

The directory device information table CT2 will be described while referencing FIG. 4. The directory device information table CT2 contains the information on the directory to mounting the target device Dev, the information for the target device Dev on which the directory is mounted, and the information of the logical device LDEV corresponding to the directory. Note that as will be described later, when using the copy on write type snapshot used by the virtual volume, the same logical device LDEV is allocated to the plurality of secondary directories. In this case, it is possible to determine whether or not the logical device LDEV is mounted by whether or not the mount device information is NULL (unmounted or not mounted). With the example in FIG. 4, the target device Dev1 is mounted in the secondary directory (/mnt/ss/home_s1), and the logical device LDEV corresponding to the secondary directory (/mnt/ss/home_s1) is the LDEV1. Also, the target device Dev is not mounted on the secondary directory (/mnt/ss/home_s2), and the logical device corresponding to the secondary directory (/mnt/ss/home_s2) is the LDEV2.

The device mount information table CT3 will be described while referencing FIG. 5. The device mount information table CT3 shows the directory that is currently mounted in the target device Dev. With the example in FIG. 5, the secondary directory (/mnt/ss/home_s1) is mounted in the target device Dev.

The usable device information table CT4 will be described while referencing FIG. 6. The usable device information table CT4 is the table indicating the usable target devices Dev. With the example in FIG. 6, the primary directory (/print/home) is mounted in the target device Dev0, and the secondary directory (/mmt/ss/home_s1) is mounted in the target device Dev1.

The various types of programs and modules stored in the memory 22 of the storage device system 20 will be described while referencing FIG. 7 to FIG. 12. FIG. 7 is an explanatory drawing that conceptually shows the various types of programs and modules stored in the memory 22 of the storage device system 20 contained in the storage system of the first embodiment. FIG. 8 is an explanatory drawing showing an example of the table for storing the device attachment information. FIG. 9 is an explanatory drawing showing an example of the table for storing the device attachment information when the virtual volume is used. FIG. 10 is an explanatory drawing showing an example of the table for storing the snapshot management information. FIG. 11 is an explanatory drawing showing an example of the table for storing the snapshot detailed management information. FIG. 12 is an explanatory drawing showing an example of the table for storing the snapshot detailed management information.

The memory 22 stores the command processing program CP for interpreting commands received from the computer 10 and executing the requested processes, the device attachment information table ST1, the device attachment information table ST2 when using the virtual volume, the snapshot management information ST3, the snapshot detailed management information ST31 and ST32, the address mapping information table ST4, and the file management information table ST5.

The command management program CP is a program for acquiring snapshots for the storage device system 20, and for realizing the execution of access (read/write) to the requested logical device (snapshot file), and the command management program CP contains several execution modules. The Input/Output request reserve module Ms1 receives access requests from the computer 10. When the Input/Output request reserve module Ms1 receives the access request, the allocation change module Ms3 allocates the logical device LDEV for which access is requested to the identified target device TD. To suitably allocate the logical device LDEV to the identified target device TD, the allocation change module Ms3 comprises three more modules, the allocation decision module Ms4, the allocation release module Ms5, and the allocation action module Ms6.

The allocation decision module Ms4 determines whether the identified target device TD for which there has been a request for allocation of the logical device LDEV has already had another logical device LDEV allocated (attached). Specifically, as described above, in this embodiment, since a plurality of logical devices LDEV may be allocated to the target device TD, this determination is necessary.

The allocation release module Ms5 cancels the allocation of the logical device LDEV to the identified target device TD. As a result, it is possible to allocate the logical device LDEV for which access is requested to the identified target device TD. The allocation action module Ms6 allocates the requested logical device LDEV for which access has been requested to the identified target device TD. The allocation and allocation release of the logical device LDEV to the target device TD is realized by the switching of the path to the logical device LDEV.

The point in time copy module Ms2 is module for executing the acquisition of the so-called snapshot files for the storage device system 20. For the acquisition of snapshots, creation of the secondary volumes for the primary volumes, copying of the primary volume data to the secondary volume or saving of the data subject to updating for the primary volume to the secondary volume, and updating of the snapshot management information are executed.

The device attachment information table ST1 will be described while referencing FIG. 8. Described in the device attachment information table ST1 is the logical device LDEV allocated (attached) to the target device TD. With the example in FIG. 8, the logical device LDEV0 is attached to the target device TD0, the logical device LDEV1 is attached to the target device TD1, and the logical device LDEV is not attached to the target device TD2.

The device attachment information table ST2 when using the virtual volume is described while referencing FIG. 9. The virtual volume is used when using the copy on write type snapshot. Specifically, with the copy on write type snapshot, the data before updating (difference data) of the data that is subject to updating (correction) for the primary volume is stored together with the information at the time of update in a storage pool formed by a plurality of logical devices. When access is requested to a snapshot file at an identified point in time, the computer 10 forms the virtual volume using a group of difference data from the identified time and thereafter, and attaches this to the corresponding logical device LDEV. The computer 10 uses the data stored in the current primary volume and the difference data group to create a snapshot file of the identified point in time.

When using the virtual volume, the device attachment information table ST2 stores the logical device for attaching the virtual volume (snapshot file), the information of the logical device LDEV for which the snapshot file primary volume is attached, and the snapshot ID. With the example in FIG. 9, the snapshot is not acquired, and when the snapshot is acquired later and the logical device LDEV1 is shared by the snapshot ID 1 to 3, one of the values 1 to 3 is stored in the space for the LDEV1 snapshot ID.

The snapshot management information table ST3 will be described while referencing FIG. 10. Contained in the snapshot management information table ST3 comprised by the storage device system 20 are the status indicating whether or not each of the logical devices LDEV is in a pair state with any of the other logical devices LDEV, the pair attribute indicating whether the logical device LDEV in the pair state is the primary or the secondary logical device, and the address of pair information for storing the pointer indicating the information of the pair logical device LDEV that is the subject. With the example in FIG. 10, the logical devices LDEV0 and LDEV1 are in a paired state, with the logical device LDEV0 being the copy source primary logical device, and the logical device LDEV1 being the copy destination (snapshot file storage destination) secondary logical device. There is no snapshot file stored in the logical device LDEV2, the status is simplex (state without creating a pair), and the pair attribute is NULL.

Referencing FIG. 11 and FIG. 12, the primary snapshot detailed management information table ST31 and the secondary snapshot detailed management information table ST32 which are indicated by the pointer contained in the subject pair information of the snapshot management information table ST3 will be described. Included in the primary snapshot detailed management information table ST31 are the snapshot ID of the secondary logical device in a paired relationship with the primary logical device, the logical device number, and the acquisition status indicating whether or not the snapshot has already been acquired. With the example in FIG. 11, the logical device LDEV1 for which the snapshot ID=0 is registered as the pair logical device LDEV. Included in the secondary snapshot detailed management information table ST32 is information of the primary logical device that is in a paired relationship with the secondary logical device. With the example in FIG. 12, the primary logical device LDEV0 is registered in the secondary logical device LDEV1 as the pair logical device LDEV.

Note that when using the virtual volume, the snapshot management information table ST3 logical device number, the primary snapshot management information table ST31 primary logical device number, and the secondary logical device number, as well as the secondary snapshot management information table ST32 primary logical device number and the secondary logical device number each indicate the virtual volume number.

When the volume that is subject to access is a virtual volume, the address mapping information table ST4 stores the address mapping information that is the information for linking the virtual volume address and the actual address of the pool area that constitutes the virtual volume. Specifically, the address mapping information is information used for managing the actual storage position of each data for pool areas for which specification using a volume number is not possible by managing using the address of each data for the virtual volume. Note that when the volume subject to access is an actual volume, it is possible to specify the storage position of the data using the volume number.

The file management information table ST5 stores file management information for managing the directory in which files are stored. Note that this will be described in detail later.

The access process that is executed when accessing the mirroring type snapshot file will be described while referencing FIG. 13 and FIG. 14. FIG. 13 is an explanatory drawing showing the typical correlation between the snapshot file information SS and the target device information Dev recognized by the file system of the computer 10 and the target device TD and the logical device LDEV (snapshot file actual information) for the storage device system 20. FIG. 14 is a flow chart showing the processing routine executed for the process of accessing the mirroring type snapshot file.

With FIG. 13, the primary volume file recognized by the client computer 30 (31) is represented as file P, and the snapshot files are represented as snapshot files S to Sn, and the actual primary volume file is represented as the file Pr and the actual snapshot file is represented as the snapshot file Sr1 to Srn. The primary volume file P and the snapshot files S1 to Sn are identified by the directory SS, and the actual snapshot files Sr1 to Srn are identified by the logical device LDEV. With the example in FIG. 13, the target device Dev0 is mounted on the primary volume file P. The snapshot files S1 to S3 which are the secondary volume files of the primary volume file may be exclusively mounted respectively in the target device Dev1. With FIG. 13, there is an access request to the snapshot file S1, so the directory of the snapshot file 51 is mounted in the target device Dev1. Each of the target devices Dev recognized by the computer 10 is uniquely correlated respectively to the target device TD for the storage device system 20. The storage device system 20 comprises a plurality of target devices TD, and a plurality of logical devices LDEV (actual snapshot files) are attached to one target device TD. For example, the primary volume file Pr is attached to the target device TD0, and the plurality of actual snapshot files Sr1 to Sr1 are exclusively attached to the target device TD1. With the example in FIG. 13, the target device TD1 is attached to the logical device LDEV1 that stored the actual snapshot file Sr1. Specifically, the logical device LDEV is attached to the target device TD for the storage device system 20 so as to correspond to the mounting of the target device Dev to the directory SS for the computer 10.

When there is a request for access to the snapshot file Sn of an identified generation for the primary volume file P from the client computers 30 and 31, the flow chart shown in FIG. 14 is executed. The CPU 11 uses the snapshot management information table CT1 stored in the memory 12 and retrieves the directory SS in which the requested snapshot file Sn is stored (step SC100). In specific terms, the directory SS for which access is requested is retrieved using the snapshot file ID (identifier) sent from the client computers 30 and 31. For example, when a request to access the snapshot for which ID=1 for /mnt/home is received from the client computer 30, then access to the directory (/mnt/ss/home_s1) will be requested.

The CPU 11 uses the usable device information table CT4 to retrieve the target device Dev used for accessing the retrieved directory (step SC110). Specifically, the usable target device Dev is retrieved (identified). With the example of the usable device information table CT4 shown in FIG. 6, the target device Dev1 may be used for the directory (/mnt/ss/home_s1). Following, with a specific example, the request directory will be (/mnt/ss/home_s1), and the retrieved target device Dev will be Dev1.

The CPU 11 uses the directory device information table CT2 and determines whether or not the retrieved target device Dev is mounted in the requested directory (step SC120). In specific terms, with the example shown in FIG. 4, at the directory device information table CT2, a determination is made of whether or not the retrieved target device Dev is mounted in the request directory (step SC120: Yes), and even if the target device Dev is already mounted in the request directory, the requested snapshot file Sr is already attached to the target device TD corresponding to the storage device system 20 as well, so this processing routine ends. Specifically, the client computers 30 and 31 are in a state capable of accessing the snapshot file S1.

When the CPU 11 determines that the retrieved target device Dev is not mounted in the request directory (step SC120: No), a determination is made of whether or not the retrieved target device Dev is mounted in another directory (step SC130). In specific terms, the CPU 11 determines whether or not the mount device information in the request directory for the directory device information table CT2 is NULL, and also whether or not the retrieved target device Dev is registered in the mount device information in another directory. For example, when the request directory is (/mnt/ss/home_s2), and the identified target device is Dev1, with the example in FIG. 4, the target device Dev1 is mounted in the directory (/mnt/ss/home_s1), and the mount device information of the request directory (/mnt/ss/home_s2) is NULL, so the retrieved target device Dev is mounted in another directory.

When the CPU 11 determines that the retrieved target device Dev is mounted in another directory (step SC130: Yes), the retrieved target device information Dev is unmounted from the other directory (step SC140). In specific terms, the CPU 11 invalidates, in other words, nullifies, the mount device information of the other directory (/mnt/ss/home_s1) in which the retrieved target device Dev1 stored in the directory device information CT2 is mounted, and the directory information of the target device Dev1 for the device mount information table CT3.

When the CPU 11 determines that the retrieved target device Dev is not mounted in the other directory (step SC130: No), step SC140 is skipped, and the process moves to step SC150.

At step SC150, the CPU 11 transmits to the storage device system 20 the access request containing the identification information for identifying the logical device LDEV to be attached to the retrieved target device Dev. For the identification information, the information of the logical device corresponding to the retrieved target device Dev retrieved for the directory device information table CT2 is used. In specific terms, information for identifying the logical device LDEV1 is sent.

When the CPU 21 of the storage device system 20 receives an access request from the computer 10, the other logical device LDEV that is attached to the target device TD uniquely corresponding to the retrieved target device Dev is detached (SS100). In specific terms, the CPU 21 nullifies the LDEV that is attached to the retrieved target device TD in the device attachment information table ST1.

The CPU 21 attaches the logical device identified by the identification information received from the computer 10 to the target device TD from which the logical device LDEV is detached (step SS110). In specific terms, the CPU 21 registers the LDEV1 to the LDEV that is attached to the concerned target device TD in the device attachment information table ST1.

The CPU 21 transmits a detachment/attachment completion report to the computer 10 (SS12), and this processing routine ends.

When the CPU 11 of the computer 10 receives the detachment/attachment completion report from the storage device system 20, the requested directory is mounted in the retrieved target device information Dev (step SC160), and this process routine ends. In specific terms, the CPU 11 registers the retrieved target device information Dev to the mount device information of the directory information in the directory device information table CT2, and registers the request directory in the directory information of the retrieved target device information Dev in the device mount information table CT3. For example, when the request directory is (/mmt/ss/home_s1), the retrieved target device information Dev1 is registered in the mount device information of the request directory (/mnt/ss/home_s2) in the directory device information table CT2, and the request directory (/mnt/ss/home_s2) is registered in the directory information of the retrieved target device information Dev in the device directory information table CT3.

Next, while referencing FIG. 15, the process for acquiring the mirroring type snapshot file is described. FIG. 15 is a flow chart showing the processing routine that is executed when acquiring the mirroring type snapshot file. Note that using FIG. 14 for description, a simple description is given regarding the same process as the steps in the process of accessing the snapshot files.

The CPU 11 of the computer 10 for which a request is made to acquire snapshot files from the client computers 30 and 31 searches the request directory for storing the requested snapshot (step SC200) and retrieves the target device information Dev correlated to the request directory (step SC210). In specific terms, the CPU 11 uses the snapshot management information table CT1, searches directories indicating an acquisition state of not being acquired, and, for example, identifies the request directory in low to high sequence of the snapshot ID. The CPU 11 retrieves the target device Dev corresponding to the request directory from the usable device information table CT4, and identifies the corresponding logical device LDEV using the directory device information table CT2.

The CPU 11 transmits to the storage device system 20 information of the identified logical device as well as the snapshot file acquisition request (step SC220).

The CPU 21 of the storage device system 20 detaches the target device TD corresponding uniquely to the retrieved target device Dev from the other logical device LDEV (step SS200), and attaches the identified logical device LDEV to the target device TD for which the other logical device LDEV was detached (step SS210). The specific procedure was described with the description of SS100 and SS110 of FIG. 14.

The CPU 21 creates a secondary volume of the primary volume in the identified logical device LDEV, and acquires the snapshot file (step SS220). In specific terms, a copy of the primary volume is generated for the identified logical device LDEV.

The CPU 21 updates the snapshot management information table ST3 (step SS230), sends the normal completion report to the computer 20 (step SS240), and ends this processing routine. A specific description will be given regarding the procedure for updating the snapshot management information table ST3. The CPU 21, in the snapshot management information table ST3, updates the status of the logical device LDEV newly stored in the snapshot file to “Pair,” and updates the pair attribute to “Secondary.” The CPU 21, in the primary snapshot management information table ST31, registers the number of the logical device LDEV newly stored in the snapshot file to the logical device number of the new snapshot ID, and updates the acquisition status of the new snapshot ID to already acquired. The CPU 21, in the secondary snapshot management information table ST32, registers the logical device LDEV0 to the primary logical device of the logical device LDEV in which the snapshot file is newly stored.

When the computer 10 receives the normal completion report from the storage device system 20, this processing routine ends.

According to the storage system 100 of the first embodiment described above, at the computer 10, when the access request is input from the client computers 30 and 31, the target device Dev (TD) is mounted in the directory SS in which the requested snapshot file is stored, so it is possible to effectively use the target device Dev resources. Specifically, according to the storage system 100 of the first embodiment, it is possible to mount a plurality of directory SS on one target device Dev, so in contrast with conventional technology, it is not necessary to maintain the resources of the target device for each directory. As a result, for the overall storage system 100, it is possible to reduce the volume of resources of the target device Dev to be allocated to the snapshot files. Therefore, it is possible to reduce or eliminate the marked resource insufficiency of the target device Dev (TD) for the snapshot system for which many snapshot files are generated at an identified timing.

Furthermore, it is possible to make it look as if the snapshot processing was executed by the computer 10 to the client computers 30 and 31, and also to have the actual execution of the snapshot processing be executed on the storage device system 20 side, so it is possible to effectively use the other file processing functions provided by the computer 10.

Note that the computer 10 may also request acquisition of the snapshot file to the storage device system 20 without identifying in advance the directory for storing a new snapshot file. In this case, after acquisition of the snapshot file, the information of the logical device LDEV for which the snapshot file is created is received from the storage device system 20, and the various tables may be updated. Alternatively, at the computer 10 and the storage device system 20, when a new snapshot file is created, if a rule is set for storing the snapshot files in the low to high sequence of the open logical devices LDEV and directories, it is possible not to execute the step SC200 or the step SC210 executed by the computer 10.

Second Embodiment

The copy on write type snapshot file process is described while referencing FIG. 16 to FIG. 18. FIG. 16 is an explanatory drawing typically showing the correlation of the snapshot file information SS and the target device information Dev recognized by the file system of the computer 10, the target device TD and the logical device LDEV for the storage device system 20, and the logical device LDEV and the snapshot data group stored in the storage pool. FIG. 17 is a flow chart showing the processing routine executed for the routine for accessing the copy on write type snapshot file. FIG. 18 is a flow chart showing the processing routine executed when acquiring the copy on write type snapshot file. Note that except for the point of the snapshot type being the copy on write type, this is the same as the mirroring type snapshot process described using FIG. 13 to FIG. 15, so for the same points, a detailed explanation is omitted, so the description will focus on the difference points.

With FIG. 16, the primary volume file for the computer 10 recognized by the client computer 30 (31) is represented as the file P, and the snapshot files are represented as the snapshot files S to Sn. The actual primary volume file for the storage device system 20 is represented as the file Pr, the update data (difference data) at an identified point in time is represented as Sd1 to Sd3, and the virtual volumes formed on the logical device LDEV during access to the snapshot file are represented as VS1 to VSn. The primary volume file P and the snapshot files S1 to Sn are identified by the directory SS, and the actual snapshot files Sd1 to Sdn are identified by the logical device LDEV. With the example in FIG. 16, the target device Dev0 is mounted in the primary volume file P. The snapshot files S1 to S3 which are the secondary volume files of the primary volume file are respectively able to be mounted exclusively in the target device Dev1. With the example in FIG. 16, there is a request for access to the snapshot file S1, so only the directory of the snapshot file S1 is mounted in the target device Dev1. Each of the target devices Dev recognized by the computer 10 is uniquely correlated respectively to the target devices TD for the storage device system 20. The computer 10 uses the difference data of the primary volume file P to generate the snapshot file at an identified point in time and to provide this to the client computers 30 and 31.

The storage device system 20 comprises a plurality of target devices TD, and a unique logical device LDEV (virtual volume VS) is attached to one target device TD. The update data (difference data) Sd1 to Sd3 at an identified point in time are stored in the storage pool Sp formed by the logical device LDEV. When a request to access a snapshot file of an identified generation is received, the storage device system 20, for example with the example in FIG. 16, attaches the difference data Sr1 to the logical device LDEV, and forms the virtual volume VS1 on the logical device LDEV1. The plurality of difference data Sr1 to Sr3 are exclusively attached to the logical device LDEV. Specifically, the difference data Sr is attached to the logical device LDEV for the storage device system 20 so as to correspond to the mounting of the target device Dev to the directory SS in the computer 10.

When a request to access the snapshot file Sn of an identified generation is made to the primary volume file P from the client computers 30 and 31, the flow chart shown in FIG. 17 is executed. The CPU 11 uses the snapshot management information table CT1 stored in the memory 12 to retrieve the directory SS in which the requested snapshot file Sn is stored (step SC300).

The CPU 11 retrieves the target device Dev used for accessing the retrieved directory using the usable device information table CT4 (step SC310). The CPU 11 determines whether or not the target device Dev retrieved using the directory device information table CT2 is mounted in the requested directory (step SC320). Note that when using the virtual volume, for the directory device information table CT2 shown in FIG. 4, the same logical device LDEV is allocated to the plurality of directories SS.

When the CPU 11 determines that the retrieved target device Dev is mounted in the request directory (step SC320: Yes), this processing routine ends. The client computers 30 and 31 are in a state for which it is possible to access the snapshot file S1.

When the CPU 11 determines that the retrieved target device Dev is not mounted in the request directory (step SC320: No), a determination is made of whether the retrieved target device Dev is mounted in another directory (step SC130). When the CPU 11 determines that the retrieved target device Dev is mounted in another directory (step SC330: Yes), the retrieved target device information Dev is unmounted from the other directory (step SC340).

When the CPU 11 determines that the retrieved target device Dev is not mounted in another directory (step SC330: No), step SC140 is skipped, and the process moves to step SC350.

At step SC350, the CPU 11 transmits to the storage device system 20 the access request containing the identification information for identifying the difference data to be attached to the retrieved target device Dev. The target device Dev information, primary volume information, and snapshot ID are used for the identification information.

When the CPU 21 of the storage device system 20 receives an access request from the computer 10, the CPU 21 converts the information of the target device TD uniquely corresponding to the retrieved target device Dev to the information of the corresponding logical device LDEV (step SS300). Specifically, the logical device LDEV uniquely corresponding to the target device TD is identified.

The CPU 21 detaches the other snapshot data Sd that is attached to the concerned logical device corresponding to the retrieved target device TD (step SS310). In specific terms, the CPU 21 nullifies the primary logical device information of the concerned logical device and the snapshot ID in the device attachment information table ST2.

The CPU 21 attaches the snapshot datan identified by the identification information received from the computer 10 to the logical device LDEV from which the other snapshot data Sd was detached (step SS320). In specific terms, in the device attachment information table ST2, the CPU 21 registers the received primary logical device information in the concerned logical device LDEV, and registers the received snapshot ID in the snapshot ID. For example, when the primary logical device is LDEV0 and the snapshot ID is 1, in the device attachment information table ST2, “LDEV0” is registered in the primary logical device of the concerned logical device LDEV, and “1” is registered in the snapshot ID.

The CPU 21 transmits the detachment/attachment completion report to the computer 10 (SS330), and this processing routine ends.

When the CPU 11 of the computer 10 receives the detachment/attachment completion report from the storage device system 20, the requested directory is mounted in the retrieved target device information Dev (step SC360), and this processing routine ends.

Next, the process for acquiring the mirroring type snapshot file is described while referencing FIG. 18.

The CPU 11 of the computer 10 for which a request was made to acquire the snapshot file from the client computers 30 and 31 searches the request directory for storing the requested snapshot (step SC400), and retrieves the target device information Dev correlated to the request directory (step SC410). The specific procedure was already described with the first embodiment.

The CPU 11 transmits to the storage device system 20 the information of the identified logical device as well as a request for acquisition of the snapshot file (step SC420).

When the CPU 21 of the storage device system 20 receives an access request from the computer 10, it converts the information of the target device TD uniquely corresponding to the retrieved target device Dev to the information corresponding logical device LDEV (step SS400). The CPU 21 detaches the other snapshot data Sd attached to the concerned logical device corresponding to the retrieved target device TD (step SS410).

The CPU 21 creates the secondary volume for storing the difference data Sr in the storage pool Sp, and acquires the snapshot file (step SS420). In specific terms, one or a plurality of data copies before updating corresponding to the part that is updated (changed) in the primary volume is created and stored in the secondary volume. Information for identifying the snapshot generation is correlated to each data, and by using this identification information, it is possible to identify the difference data Sr relating to the identified generation.

The CPU 21 updates the snapshot management information table ST3 (step SS430). The procedure for updating the snapshot management information table ST3 will be described specifically. Note that when using the virtual volume, the logical device number of the snapshot management information table ST3 and the snapshot detailed management information table ST31 and ST32 means the virtual volume number.

In the snapshot management information table ST3, the CPU 21 updates the status of the logical device LDEV for providing the virtual volume to “Pair” and updates the pair attribute to “Secondary” with attachment of the snapshot data. In the primary snapshot management information table ST31, the CPU 21 registers the number of the logical device LDEV for providing the virtual volume to the logical device number of the new snapshot ID, and updates the acquisition status of the new snapshot ID to already acquired. In the secondary snapshot management information table ST32, the CPU 21 registers the logical device LDEV0 to the primary logical device of the logical device LDEV for providing the virtual volume.

The CPU 21 attaches the snapshot datan identified by the identification information received from the computer 10 to the logical device LDEV form which the other snapshot data Sd was detached (step SS440), the CPU 21 sends a normal completion report to the computer 10 (step SS450), and this processing routine ends.

When the computer 10 receives the normal completion report from the storage device system 20, this processing routine ends.

As described above, according to the storage system 100 of the second embodiment, even when the virtual volume is used, with the computer 10, the target device Dev is mounted on the directory SS in which the snapshot file requested from the client computers 30 and 31 is stored, so it is possible to effectively use the resources of the target device Dev. Also, with the storage device system 20, it is possible to exclusively allocate a plurality of difference data Sr to the logical device LDEV for providing the virtual volume, so in contrast to the conventional technology, it is not necessary to maintain the resources of the target device for each difference data. As a result, it is possible to reduce the volume of resources of the target device Dev and TD for allocation to the snapshot files for the overall storage system 100.

Note that with the computer 10, by having information of whether the volume subject to access is an actual volume or a virtual volume, or by inquiring with the storage device system 20, may identify whether the volume subject to access is an actual volume or a virtual volume.

Variation Example of the Second Embodiment

A variation example of the storage system 100 of the second embodiment is described while referring to FIG. 19 to FIG. 21. FIG. 19 is an explanatory drawing typically showing the correlation between the snapshot file information and target device information recognized by the computer file system, the storage device system target device and logical device, and the primary side volume file data groups and the snapshot data groups stored in the logical device and the storage pool. FIG. 20 is an explanatory drawing showing an example of the table that stores the device attachment information for the variation example. FIG. 21 is an explanatory drawing showing an example of the table that stores the snapshot detailed management information for the variation example.

With this variation example, not only the snapshot files S1 to Sn but also the primary volume file P0 of the snapshot files S1 to Sn are formed using a virtual volume. Note that to make the description easier, in FIG. 19, only the snapshot files S1 to Sn for the primary volume file P0 are shown, but it is obvious that the snapshot files S1 to Sn also exist in the same way for primary volume files P1 and P2.

In FIG. 19, the primary volume files for the computer 10 recognized by the client computer 30 (31) are represented as files P0 to P2, and the snapshot files are represented as snapshot files S1 to Sn. For the storage device system 20, the virtual volume corresponding to the primary volume file is represented as VPr, and the virtual volumes formed on the logical device LDEV during access of the snapshot files are represented as VS1 to VSn. Also, the actual data of the primary volume files for the storage pool Sp are represented as files Pd0 to Pd2, and the snapshot update data (differential data) at a specified point are represented as Sd1 to Sd3. The primary volume files P0 to 2 and the snapshot files S1 to Sn are specified by the directory SS, the actual data of the primary volume files are files Pd0 to Pd2, and the actual snapshot files Sd1 to Sdn are specified by the logical device LDEV.

With the example in FIG. 19, the primary volume files P0 to P2 are respectively mounted exclusively in the target device Dev0, and the snapshot files S1 to S3 that are secondary volume files of the primary volume files are respectively mounted exclusively in the target device Dev1. Also, with the example in FIG. 19, the snapshot of the primary volume file P0 is used as an example, so only the directory of the primary volume file P0 is mounted in the target device Dev0, and furthermore, there is a request for access to the snapshot file S1, so only the directory of the snapshot file S1 is mounted in the target device Dev1.

The storage device system 20 is equipped with a plurality of target devices TD, and the virtual volumes VPr and VS (logical device LDEV) are uniquely attached to one target device TD. The actual data Pd0 to Pd2 of each primary volume file are stored in the storage pool Sp formed by the logical device LDEV. When an access request is received for any of the primary volume files, the storage device system 20, for example with the example in FIG. 19, attaches the logical device LDEV0 to the primary volume file actual data Pd0, and forms the virtual volume VPr on the logical device LDEV0. The plurality of actual data Pd0 to Pd2 are exclusively attached to the logical device LDEV. Specifically, so as to correspond to the mounting of the target device Dev to the directory SS for the computer 10, the actual data Pd0 to 2 are attached to the logical device LDEV of the storage device system 20. Note that the attachment of the actual data Pd0 to 2 to the logical device LDEV for the storage device system 20 is executed by the allocation switching module Ms3.

The device attachment information table ST4 used when the primary volume file is a virtual volume is described while referring to FIG. 20. The device attachment information table ST4 stores the logical device for attaching the virtual volume (primary volume file), the primary volume file ID, and the snapshot ID. With the example shown in FIG. 20, the identification information (ID) of the actual data attached to the logical device LDEV0 from among the actual data Pd0 to Pd2 for the storage pool Sp is stored in the logical device LDEV0. Note that when none of the actual data is attached to the logical device LDEV0, the primary volume file ID is NULL. Snapshots are not acquired with the example in FIG. 20, but snapshots are acquired later.

The primary side snapshot detailed management information table ST4 used when the primary volume file is a virtual volume is described while referring to FIG. 21. The primary side snapshot detailed management information table ST4 contains the primary side logical device number, the snapshot ID of the secondary side logical device that has a pair relationship with the primary side logical device, the secondary side logical device number, and the acquisition status that indicates whether the snapshot has already been acquired. With the example in FIG. 21, the upper level shows an example for which a virtual volume is not allocated to the primary volume file, the primary side logical device number is NULL, and snapshots have not been acquired. Meanwhile, the lower level shows that a virtual volume is allocated to the primary volume file and LDEV10 has been registered for the primary side logical device number. Also, one snapshot has been acquired, and the logical device LDEV1 for which the snapshot ID=1 is registered as the pair logical device LDEV. Note that the primary side logical device number and the secondary side logical device number of the snapshot detailed management information table ST4 respectively indicate virtual volume numbers.

Third Embodiment

With the first and second embodiments noted above, described was a case for which the snapshot file is stored using the storage system 100 for which the computer 10 and the storage device system 20 are stored in the same case, but as shown in FIG. 22, it is possible to apply this in the same way for storage systems for which the computer 10 and the storage device system 20 are constructed separately. FIG. 22 is an explanatory drawing showing the schematic structure of the storage system 100A related to other embodiments.

The storage system 100A of FIG. 22 comprises a computer 10A and a storage device system 20A accessed by the computer 10A. The client computers 30 and 31 and the management server 50 are connected via the network 40 or directly connected to the storage system 100A. Typically there is no compatibility between the commands used for the file system of the computer 10A and the commands used for the storage device system 20A, so it is necessary to define a special command and to send instructions from the computer 10A to the storage device system 20A.

The computer 10A of FIG. 22 is connected to the client computers 30 and 31 via the network 40. The computer 10 internally comprises a central processing unit (CPU) 11A, a memory 12A, a LAN interface 13A, a storage interface 14A, and an FC interface 15A. The CPU 11A, the memory 12A, and each interface 13, 14, and 15 are mutually connected via a bus.

The storage device system 20 comprises a central processing unit (CPU) 21A, a memory 22A, an FC interface 23A, a plurality of disk devices 24A, a disk interface 25A, a storage interface 26A, and a LAN interface 27A.

The FC interfaces 15A and 23A are connected by an optic fiber cable or copper wire, for example, and commands and data are sent and received using a fiber channel protocol between the computer 10 and the storage device system 20. The management server 50 is connected to the storage device system 20A via the LAN interface 27A, and commands and data are sent and received.

The disk device 24A is a disk array device formed by RAID construction by a plurality of magnetic hard disk drives, and one or a plurality of storage areas, specifically, logical devices (LDEV), are provided by a plurality of hard disk drives, or one or a plurality of logical devices is provided by one hard disk drive.

The CPU 21A is connected to the disk device 24A via the disk interface 25A. The disk interface 25A converts the logic address transmitted from the CPU 21A to the logic block address, and access is realized to each logical device by the CPU 21A.

The storage interfaces 14A and 26A are interfaces for exchanging special commands for indicating the detachment/attachment of the logical device LDEV to the target device TD between the computer 10A and the storage device system 20A. The special commands are preset standard read/write commands to the logical device LDEV (command device), and, for example, commands for indicating the detachment/attachment of the logical device LDEV to the target device TD and commands for indicating the acquisition of a snapshot are added. The computer 10A transmits special commands to the storage interface 26A of the storage device system 20 via the storage interface 14A. When the received command is a read/write command to the command device, the storage interface 26A interprets the detachment/attachment command of the logical device LDEV to the added target device TD, executes the detachment/attachment process of the logical device LDEV to the target device TD, and gives instructions to execute the snapshot acquisition process.

Fourth and Fifth Embodiments

With the storage system 100 of the first and second embodiments noted above, described were examples of storing snapshot files, but it is also possible to try to reduce the target device Dev and TD resource volume and effectively utilize the storage system 100 in the same way for storage of typical files. In this case, the computer 10 side snapshot management information table CT1 and the storage device system 20 side snapshot management information table ST3 and the snapshot detailed management information tables ST31 and ST32 are not necessary.

The case when using the storage system 100 and 100A for the typical file system is described while referring to FIG. 23 to FIG. 29. FIG. 23 is an explanatory drawing typically showing the correlation between the file information and target device information recognized by the computer file system, and the storage device system target device and logical device for the fourth embodiment. FIG. 24 is an explanatory drawing showing in detail the file management information table used for the fourth embodiment. FIG. 25 is a flow chart showing the processing routine executed for the process of accessing the files for the storage device system of the fourth embodiment. FIG. 26 is an explanatory drawing typically showing the correlation between the file information and target device information recognized by the computer file system and the file data groups of the storage device system. FIG. 27 is an explanatory drawing showing an example of a table that stores the device attachment information of the fifth embodiment. FIG. 28 is a flow chart showing the processing routine executed for the process of accessing the virtual volume file for the storage device system of the fifth embodiment. FIG. 29 is an explanatory drawing showing an example of the client identification table that the computer 10 has.

Note that with the description below, the description is of an example using the constitution shown in FIG. 1 using the code numbers shown in FIG. 1, but it is obvious that this can also be used in the same way on the constitution shown in FIG. 22 as well. When using on a typical file system, one target device Dev is shared by a plurality of client computers, so it is necessary to have the target device mounted on a suitable directory according to the client computer. Possible means for resolving this necessity include, for example:

(a) Creating a directory for each client computer under the same target device

(b) Using the IP address information of the client computer

In the former case, using the means described for the first embodiment or second embodiment, it is possible to mount the target device on a suitable directory according to the client computer. Specifically, by having each snapshot file S1 to Sn for the first embodiment be a directory (file) dedicated to each client computer, it is possible for the computer to mount the target device on a suitable directory, and for the storage device system 20 to attach the logical device LDEV to a suitable target device TD. With the storage system 100 of the first embodiment, each time the necessity arises for access to the snapshot file, mounting of the target device to the directory and attachment of the logical device LDEV to the target device TD are executed, so it is possible to process requests for access to a snapshot file as a request for access to a file from the client computer. Note that the computer 10 and the storage device system 20 have the same tables except for tables relating to snapshots.

Following, the first resolution means (a) is described as the fourth embodiment while referring to FIG. 23 to FIG. 25. With FIG. 23, the files recognized by the client computer 30 (31) are represented as files F1 to Fn, and the actual file data stored in the storage device system 20 are represented as actual files L1 to Ln. Each file F is specified by a directory FG, and the actual files L1 to Ln are specified by the logical device LDEV. For example, the files F1 to F3 can be respectively exclusively mounted in the target device Dev1. With the example in FIG. 23, there is a request for access to the file F1, so the directory of the actual file L1 is mounted on the target device Dev1.

Each target device Dev recognized by the computer 10 is respectively uniquely correlated to a target device TD of the storage device system 20. The storage device system 20 has a plurality of target devices TD, and a plurality of logical devices LDEV (actual files) are attached to one target device TD. For example, a plurality of actual files L1 to L3 are exclusively attached to the target device TD1. With the example in FIG. 23, the target device TD1 is attached to the logical device LDEV that stores the actual file L1. Specifically, so as to handle mounting of the target device Dev on the directory FG for the computer 10, the logical device LDEV is attached to the target device TD for the storage device system 20.

The file management information table ST5 is described while referring to FIG. 24. In the file management information table ST5 are correlated and stored the computer side directory FG (file name) specified by the client computer 30 and the directory information (/mnt/ss/home fN) in which are stored actual files of the storage device system 20 side.

The process of accessing the actual file for the first resolution means (a) is described while referring to FIG. 25. When the CPU 11 of the computer 10 receives a request to access the file F from the client computer 30, the attachment process already described with FIG. 14 is executed together with the storage device system 20 (step SC500, SS500). Included in the access request is identification information for identifying the actual file L that corresponds to the computer side file F for which access has been requested. For example, with the example in FIG. 22, the CPU 11 of the computer 10 finds the Dev1 as the target device Dev for accessing the request directory F1, and sends the directory information that specifies the directory L1 to be attached to the found target device Dev1 to the storage device system 20. The CPU 21 of the storage device system 20 that received the directory information attaches the logical device LDEV (L1) that stores the requested actual file data to the target device TD1 correlated uniquely to the computer side target device Dev1. When the CPU 11 of the computer 10 receives attachment completion notification from the storage device system 20, the target device Dev1 is mounted on the directory F1.

The CPU 11 of the computer 10 sends a read/write request as the access request to the storage device system 20 (SC510). The storage device system 20 that has received the read/write request determines whether or not this is a read request (step SC510), and when it is a write request (step SC510: No), it executes the requested write process (step SS520), and this processing routine ends.

When the storage device system 20 determines that this is a read request (step SC510: Yes), it executes the requested read process (step SS530), sends the read data to the computer 10 (step 88540), and this processing routine ends.

The computer 10 receives the read data from the storage device system 20 (step SC520), sends it to the client computer 30, and this processing routine ends.

Next, the second means of resolving of (a) is described as the fifth embodiment while referring to FIG. 26 to FIG. 28. With FIG. 26, the files for the computer 10 that are recognized by the client computer 30 (31) are represented as files F1 to Fn, the virtual volumes formed on the logical device LDEV during access to the files F for the storage device system 20 are represented as VS1 to VSn, and the actual data of the files for the storage pool Sp are represented as Po1 to Po3. The files F1 to Fn are specified by the directory FG, and the actual data of the files Po1 to Po3 are specified by the logical device LDEV. For example, the files F1 to F3 can respectively be exclusively mounted on the target device Dev1. With the example in FIG. 26, there is a request to access the file F1, so only the directory of the file F1 is mounted on the target device Dev1. Each target device Dev recognized by the computer 10 is respectively uniquely correlated to a target device TD for the storage device system 20.

The storage device system 20 is equipped with a plurality of target devices TD, and a unique logical device LDEV (virtual volume VS) is attached to one target device TD. The actual data of the file Po1 to Po3 are stored in the storage pool Sp formed by the logical device LDEV. When a request for access to a specific file is received, the storage device system 20 attaches the actual data Po1 to the logical device LDEV1, for example, and forms the virtual volume VS1 on the logical device LDEV1. A plurality of actual data Po1 to Po3 are exclusively attached to the logical device LDEV. Specifically, the actual data Po is attached to the logical device LDEV for the storage device system 20 so as to handle mounting of the logical device LDEV on the storage device system 20. Note that for the storage area of the actual data Po, an area correlating to the volume capacity amount of the corresponding file F is not secured in the storage pool from the start, but rather the storage area is increased according to updating of the file F. When the actual data Po is updated, the storage device system 20 adds the address of the storage area added by the update to the management addresses.

The device attachment information table ST2′ used for this embodiment is described while referring to FIG. 27. The device attachment information table ST2′ when using the virtual volume stores information of the logical device for attaching the virtual volume and of the actual data Po to be attached for forming the virtual volume. One of the actual data Pal to Po3 is set to be attached, or not attached (NULL) to the logical device LDEV0, and one of actual data Po4 to Po6 is set to be attached, or not attached (NULL) to the logical device LDEV1.

The process of accessing an actual file for the second means of resolving of (a) is described while referring to FIG. 28. When the CPU 11 of the computer 10 receives a request to access any file F from the client computer 30, a read/write request for the virtual volume VS* corresponding to any file F is sent to the storage device system 20 (SC600). Following, to make the description easy, a case when a request is issued to access the file F1 is described as an example. The CPU 21 of the storage device system 20 determines whether the actual data Po1 of the file F1 is attached to the virtual volume VS1 corresponding to the file F1 for which access is requested (step SS600). When the CPU 21 determines that the actual data Po1 is attached to the virtual volume VS1 (logical device LDEV0) (step SS600: Yes), it determines whether the access request is a read request (step SS610). When the CPU 21 determines that this is not a read request, specifically, that it is a write request (step SS610: No), the write process is executed on the virtual volume VS1, and this processing routine ends.

When the CPU 21 determines that this is a read request (step SS610: Yes), read processing is executed on the virtual volume VS1 (step SS625). Note that for this embodiment, a data value “0” is recorded in the virtual volume FS depending on the format, and the read data value is the value of the data stored in the virtual volume VS, or is “0” when write is not executed after formatting.

At step SS600, when the CPU 21 determines that the actual data Po1 is not attached to the virtual volume VS1 (logical device LDEV0) (step SS600: No), it determines whether or not the access request is a read request (step SS630). When the CPU 21 determines that this is a read request (step SS630: Yes), ALL0 is read and acquired as data (step SS640). Specifically, the subject actual data Po1 is not attached to the virtual volume VS1 and there is no data to be read, so the value “0” is returned from the read/write controller (disk controller).

When the CPU 21 determines that it is not a read request, specifically, that it is a write request (step SS630: No), the corresponding actual data Po1 is attached to the virtual volume VS1 (step SS645). Alternatively, the same as when it is a read request, there is no virtual volume VS1 to which actual data Po1 is attached as the virtual volume VS to be written, so ALL0 can be acquired. Specifically, for this embodiment, ALL0 indicates that the execution results of the request process were unsuccessful.

The CPU 21 sends the read data or the acquired data to the computer 10 (step SS650), and this process ends. The computer 10 receives the read data value or the value “0” from the storage device system 20 (step SC610), and this processing routine ends.

In the latter case, for example by comprising the table shown in FIG. 29, it is possible to mount the target device on a suitable directory for each client computer.

As shown in FIG. 29, the IP addresses for identifying each client computer and the target devices that may be used by each client computer are correlated. When the computer 10 receives the access request from the client computer, it acquires the IP address of the client computer, and determines the target device to be accessed. When the determined target device is used by another client computer, the computer 10 gives notice to the client computer that access in the identified time is impossible, and transmits an interrupt access request to the storage device system 20 after an identified time has elapsed.

Alternatively, the computer 10 transmits the interrupt access request to the storage device system 20 immediately, and provides access to the desired file to the client computer.

Even in the case of the description noted above, it is possible to try to achieve effective use of the target device resources for the storage system.

Other Embodiments

(1) The inquiry process of making an inquiry about the device capacity and status to the storage device system 20 is described while referring to FIG. 30 to FIG. 31. FIG. 30 is an explanatory drawing typically showing the correlation between the file information and target device information recognized by the computer file system and the target device and logical device of the storage device system for other embodiments. FIG. 31 is a flow chart showing the processing routine executed for the inquiry process.

With the example in FIG. 30, the file F1 is mounted in the target device Dev1 of the computer 10, and the logical device (L1) is attached to the target device TD1 of the storage device system 20. As described previously, the target device TD1 of the storage device system 20 has a unique relationship with the target device Dev1, and with this status, when the computer 10 receives an inquiry request from the client computer 30, it sends an “inquiry request” to the target device layer (Dev layer) that is the initiator port. With the example in FIG. 30, the target devices Dev 1, 2, and 5 are defined, but the target devices Dev 3 and 4 are not defined. Therefore, there is no information regarding the undefined target devices Dev 3 and 4.

The computer 10 sends an inquiry to the target ports (target device TD of the storage device system 20) via the defined target devices Dev 1, 2, and 5 (step SC700). The storage device system 20 that has received the inquiry acquires the capacity and status for the target devices TD1, 2, and 5 on the storage device system 20 side corresponding to the target devices Dev 1, 2, and 5 on the computer 10 side (step SS700).

With the example in FIG. 30, the logical device L1 is attached to the target device TD1, and logical devices are not attached to the remaining target devices TD2 and TD5. Therefore, the storage device system 20 replies with Status: Attached, Capacity: Capacity of logical device L1 for the target device TD1, and replies with Status: Unattached, Capacity: 0 for the target devices TD2 and TD5, sends this to the computer 10 (step SS710), and this processing routine ends.

The computer 10 receives the replies (step SC710). returns the received replies to the client computer 30, and this processing routine ends.

With the inquiry process above, it is possible to acquire information relating to the target device TD status and logical device capacity that the storage device system 20 has from the client computers 30 and 31. Note that in addition to sending inquiry requests directly to the storage system 100 as described above, the client computers 30 and 31 can also connect to the service host 51 via the network 40, and can send inquiry requests to the storage system 100 via the application program that the service host 51 has.

(2) With each of the embodiments described above, cases for which the storage device system comprised one computer were described, but it is also possible to comprise a plurality of computers. In this case, it is necessary to prevent overlapping use of the target devices between the computers. For example, use status of the target device is indicated to the computers, and the computers transmit access requests to the storage device system based on the concerned use status information. Alternatively, by fixing the logical device to each of the computers, specifically, by determining the target device that may be used for each of the computers, it is possible to prevent overlapping use of the target devices.

(3) For the first and second embodiments noted above, it is also possible to combine the flow chart of the process for accessing the snapshot files and the flow chart of the process for acquiring the snapshots. In this case, it is possible to access the snapshot files immediately after acquisition of the snapshots. Specifically, the target device Dev is already mounted in the directory in which the newly acquired snapshot file is stored, so it is possible to immediately access (read/write) the snapshot files.

While this invention has been described in terms of several preferred embodiments, it will be appreciated that those skilled in the art upon reading the preceding identifications and studying the drawings will realize various alterations, additions, permutations and equivalents thereof. It is therefore intended that the present invention includes all such alterations, additions, permutations, and equivalents as fall within the true spirit and scope of the invention. 

1. (canceled)
 2. A storage system comprising: a first computer; and a second computer coupled to the first computer via a network; wherein the second computer comprises: a processor; a plurality of storage areas of the second computer, which are recognized by the first computer; and a plurality of target devices of the second computer, which are recognized by the first computer; wherein the processor is configured to retrieve a request directory in which a requested snapshot file is stored, in response to a request for access to the snapshot file, and to retrieve one of the target devices used for accessing the retrieved directory.
 3. The storage system according to claim 1, wherein the processor is further configured to: determine whether the retrieved target device is mounted in the request directory; determine whether the retrieved target device is mounted in another directory when the retrieved target device is not mounted in the request directory; unmount the retrieved target device from the other directory when the retrieved target device is mounted in the other directory; transmit to a storage device system an access request containing identification information for identifying a local device to be attached to the retrieved target device; and mount the retrieved target device in the request directory when a detachment/attachment completion report is received from the storage device system.
 4. The storage system according to claim 1, wherein the plurality of target devices of the second computer at least include a target device A of the second computer, which is exclusively mounted on any of the plurality of storage areas of the second computer including a storage area A of the second computer, and wherein the processor is further configured to receive a first access request to access the storage area A of the second computer among the plurality of storage areas of the second computer.
 5. The storage system according to claim 1, wherein the plurality of target devices of the second computer at least include a target device A of the second computer, which is exclusively mounted on any of the plurality of storage areas of the second computer including a storage area A of the second computer, and wherein the processor is further configured to identify the target device A of the second computer from among the plurality of target devices of the second computer, in response to the first access request.
 6. The storage system according to claim 1, wherein the plurality of target devices of the second computer at least include a target device A of the second computer, which is exclusively mounted on any of the plurality of storage areas of the second computer including a storage area A of the second computer, and wherein the processor is further configured to exclusively mount the identified target device A of the second computer on the storage area A of the second computer.
 7. The storage system according to claim 1, wherein the plurality of target devices of the second computer at least include a target device A of the second computer, which is exclusively mounted on any of the plurality of storage areas of the second computer including a storage area A of the second computer, and wherein the processor is further configured to transmit to the storage device system a second access request to identify a storage area A of the storage device system among the plurality of storage areas of the storage device system, which corresponds to the storage area A of the second computer.
 8. The storage system according to claim 1, wherein the plurality of target devices of the second computer at least include a target device A of the second computer, which is exclusively mounted on any of the plurality of storage areas of the second computer including a storage area A of the second computer, and wherein the processor is further configured to determine whether the target device A to be mounted to the storage area A of the second computer is mounted on another storage area of the second computer.
 9. The storage system according to claim 1, wherein the plurality of target devices of the second computer at least include a target device A of the second computer, which is exclusively mounted on any of the plurality of storage areas of the second computer including a storage area A of the second computer, and wherein the processor is further configured to unmount the target device A when the target device A to be mounted to the storage area A of the second computer is mounted on the another storage area of the second computer.
 10. A method of accessing a snapshot file comprising: in response to a request for access to a snapshot file is received, retrieving a directory in which the requested snapshot file is stored; retrieving one of the target devices used for accessing the retrieved directory using a usable device information table; determining whether the retrieved target device is mounted in the request directory; determining whether the retrieved target device is mounted in another directory when the retrieved target device is not mounted in the request directory; unmounting the retrieved target device from the other directory when the retrieved target device is mounted in the other directory; transmitting to a storage device system an access request containing identification information for identifying a local device to be attached to the retrieved target device; and mounting the retrieved target device in the request directory when a detachment/attachment completion report is received from the storage device system.
 11. A storage system comprising: a first computer; and a second computer coupled to the first computer via a network; wherein the second computer comprises: a processor; a plurality of storage areas of the second computer, which are recognized by the first computer; and a plurality of target devices of the second computer, which are recognized by the first computer; wherein the processor is configured to: in response to a request for access to a snapshot file, search a request directory for storing the requested snapshot file, retrieve a target device correlated to the request directory, and identify a corresponding logical device; and transmit information of the identified logical device and a snapshot acquisition request to a storage device system. 